Skip to content

fix: Enhance Bicep Outputs for Environment Variable Configuration in .env File #1808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

Prasanjeet-Microsoft
Copy link
Contributor

Purpose

  • This PR introduces the following changes to main.bicep for seamless environment setup via azd up:
  1. Added a new output variable: DATABASE_TYPE
  2. Renamed existing outputs to match expected env variable names used in the application
  3. Ensures that .env is generated with the correct variables during deployment
  4. This will help in running the application locally and facilitate easier debugging

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

What to Check

Verify that the following are valid:

  • Run azd up and ensure the .env file correctly includes the new DATABASE_TYPE output.
  • Verify that the renamed output variables are accurately reflected and consumed by the application.
  • Confirm that the application is reading values correctly from the generated .env file.
  • Ensure that no default or fallback values are used at runtime due to missing environment variables.
  • Check that no breaking changes were introduced for existing deployments.

…ut variables to align with application environment variable expectations used during azd up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant